Skip to content

[CFI] Detail view dropdown - #106208

Open
DylanDylann wants to merge 19 commits into
Expensify:mainfrom
DylanDylann:dylann/105904-saved-expense-text-inputs
Open

DylanDylann wants to merge 19 commits into
Expensify:mainfrom
DylanDylann:dylann/105904-saved-expense-text-inputs

Conversation

@DylanDylann

@DylanDylann DylanDylann commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #105904
PROPOSAL:

Tests

Same as QA steps

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Precondition: a Control workspace with categories, tags, taxes and attendee tracking enabled, and an expense on an open report.

  1. Open the expense on a wide screen. Verify a "Details" heading, bordered fields like the create expense form, and a "Comments" heading above the thread once it has a comment.
  2. Change the amount, description, merchant and tax amount, clicking outside each. Verify each saves. Pick a new currency and date, and verify they save at once.
  3. Type (none) as the merchant, then a tax amount above what the rate allows. Verify each shows an error and doesn't save.
  4. Click Category, Tag, Tax rate, Attendees and Report. Verify each list opens attached to the field (a bottom sheet on narrow screens) and a pick saves.
  5. Open an expense on a paid report. Verify amount, merchant and date are locked, and on web hovering one offers to copy it.
  6. Create a new expense. Verify the create form works as before.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Screen.Recording.2026-11-09.at.17.00.40.mov
Android: mWeb Chrome
Screen.Recording.2026-11-09.at.16.54.13.mov
iOS: Native
Screen.Recording.2026-11-09.at.16.53.17.mov
iOS: mWeb Safari
Screen.Recording.2026-11-09.at.16.48.18.mov
MacOS: Chrome / Safari
Screen.Recording.2026-11-09.at.16.45.27.mov

@DylanDylann
DylanDylann requested review from a team as code owners November 6, 2026 11:13
@melvin-bot
melvin-bot Bot requested review from ikevin127 and removed request for a team November 6, 2026 11:13
@melvin-bot

melvin-bot Bot commented Nov 6, 2026

Copy link
Copy Markdown

@ikevin127 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot requested review from trjExpensify and removed request for a team November 6, 2026 11:13
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-09T09:33:09.587708Z
We couldn’t complete this review. Comment @codex review to try again.
a438559 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@codecov

codecov Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/SENTRY_LABEL.ts 100.00% <ø> (ø)
...AmountActionButtons/AmountCurrencyPickerButton.tsx 94.44% <100.00%> (+1.11%) ⬆️
...nents/AmountActionButtons/AmountSignFlipButton.tsx 100.00% <100.00%> (ø)
src/components/MenuItem/layout/MenuItemContent.tsx 100.00% <100.00%> (ø)
...eyRequestConfirmationList/sections/AmountField.tsx 86.59% <ø> (-0.19%) ⬇️
...onfirmationList/sections/AttendeeFieldDropdown.tsx 100.00% <100.00%> (ø)
...uestConfirmationList/sections/DescriptionField.tsx 90.90% <100.00%> (ø)
...questConfirmationList/sections/ExpenseFieldRow.tsx 100.00% <100.00%> (ø)
src/components/ReceiptAudit.tsx 70.96% <100.00%> (+3.22%) ⬆️
...rc/components/ReportActionItem/MoneyReportView.tsx 95.77% <100.00%> (+0.39%) ⬆️
... and 33 more
... and 8 files with indirect coverage changes

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: df224ebf73

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useMirroredInputValue.ts Resolved
Comment thread src/hooks/useMirroredInputValue.ts Resolved
@DylanDylann DylanDylann changed the title [CFI] Detail view dropdown- #105603 [CFI] Detail view dropdown Nov 6, 2026
@DylanDylann
DylanDylann marked this pull request as draft November 6, 2026 11:43
@DylanDylann
DylanDylann marked this pull request as ready for review November 9, 2026 09:15
@ikevin127

ikevin127 commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Screen.Recording.2026-11-09.at.18.17.26.mov

@trjExpensify

Copy link
Copy Markdown
Contributor

@DylanDylann can you fix the conflicts and then I'll run a build?

@ikevin127 ikevin127 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Request changes (non-blockers that should still be addressed).

Comment thread src/hooks/useUpdateTransactionAmount.ts Resolved
Comment thread src/CONST/index.ts Resolved
Comment thread tests/ui/MoneyRequestViewTest.tsx Resolved
@github-actions

Copy link
Copy Markdown
Contributor

🚧 shawnborton has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@shawnborton

Copy link
Copy Markdown
Contributor

Can you check my prototype for all of my following comments? Just to have as a reference point. I will start leaving comments now :)

Let's get rid of the empty state peeking through at the top here - it's no longer needed:
CleanShot 2026-11-10 at 12 02 11 PM@2x

@shawnborton

Copy link
Copy Markdown
Contributor

Check for the correct padding/spacing values of the divider + label pattern:
CleanShot 2026-11-10 at 12 02 51 PM@2x

From the proto:
CleanShot 2026-11-10 at 12 28 44 PM@2x

… of NumberWithSymbolForm, enhancing input handling and structure.
… support for borderless styles, improving visual integration within forms. Update tests to verify new styling behavior and ensure proper ref handling for currency buttons.
@DylanDylann

Copy link
Copy Markdown
Contributor Author

@shawnborton Can you review again on a new adhoc build?

@DylanDylann

Copy link
Copy Markdown
Contributor Author

The failed check on main

@github-actions

Copy link
Copy Markdown
Contributor

🚧 shawnborton has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

This comment has been minimized.

@shawnborton

Copy link
Copy Markdown
Contributor

On the receipt side, the top padding is only 12px:
CleanShot 2026-11-11 at 7 28 03 PM@2x

On the details side, it's 16px:
CleanShot 2026-11-11 at 7 28 36 PM@2x

From the proto, it should be 16px for both:
CleanShot 2026-11-11 at 7 55 28 PM@2x

@shawnborton

Copy link
Copy Markdown
Contributor

Also it seems like read-only inputs are 54px tall:
CleanShot 2026-11-11 at 7 59 00 PM@2x

When they should be 52px, like the inputs:
CleanShot 2026-11-11 at 7 59 25 PM@2x

@shawnborton

Copy link
Copy Markdown
Contributor

Select menus are also too big, they should be 52px as well but are 54px:
CleanShot 2026-11-11 at 7 59 45 PM@2x

@shawnborton

Copy link
Copy Markdown
Contributor

Otherwise feeling pretty good, let's fix those quickly but also continue our final review since this is a big one.

@ikevin127

Copy link
Copy Markdown
Contributor

Awaiting on final design nits to be fixed before taking another look. Please tag me once it's my turn at this 🙌

@DylanDylann
DylanDylann requested a review from a team as a code owner November 12, 2026 06:53
@DylanDylann

Copy link
Copy Markdown
Contributor Author

Awaiting on final design nits to be fixed before taking another look. Please tag me once it's my turn at this 🙌

@ikevin127 It’s just minor styling. I don’t think it blocks your review. It's better if you can start your next review

@DylanDylann

Copy link
Copy Markdown
Contributor Author

@shawnborton Ready for your next review

@github-actions

Copy link
Copy Markdown
Contributor

🚧 shawnborton has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

Copy link
Copy Markdown
Contributor

@shawnborton

Copy link
Copy Markdown
Contributor

Still seeing read-only inputs as 54px tall:

CleanShot 2026-11-12 at 10 57 17 AM@2x

@shawnborton

Copy link
Copy Markdown
Contributor

Other nit was fixed though. @ikevin127 I say start your review since this is a big one.

@ikevin127 ikevin127 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Request changes (non-blockers that should still be addressed).

@DylanDylann, everything from my last round is fixed. The new AmountFormField inputs don't save on Enter anymore ⚠️

Comment thread tests/ui/MoneyRequestViewTest.tsx Resolved
@trjExpensify

Copy link
Copy Markdown
Contributor

@DylanDylann are you going to be able to fix these conflicts and address the comments today? Would love to get it merged if we can. 👍

@DylanDylann

Copy link
Copy Markdown
Contributor Author

@shawnborton Fixed

Screenshot 2026-11-13 at 14 21 52

@shawnborton

Copy link
Copy Markdown
Contributor

Thanks! Continue with final review please @ikevin127 we're excited for this one.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants